Arriving Solution

Before Solution

bespoke vs off-the-shelf solution

obtain requirements from stakeholders: - Surveys: - Adv: You can get information from a lot of people quickly - Disadv: The survey may not ask the right questions. Qualitative information difficult to quantify. - Interviews: - Adv: Stakeholders can make you aware of things you hadn’t thought of, unlike with survey in which their answers are restricted - Disadv: Time-consuming. Stakeholders may give biased information. - Direct observations: - Adv: Avoids bias. - Disadv: Time-consuming. Observer can affect the process.

methods to gather info to get solution: - Examine the current system - Competing products - Organisational capabilities. Are there experts within the organisation who can be consulted? - A literature search is the term given to a systematic study to previous project reports to in an attempt to see if the problem has already been solved by someone else

Making Solution

prototype purpose: - get feedback (new requirements) - easier to understand - reduce cost/save time

testing method - Debugging: Ongoing. Happens during development - Alpha testing: The first stage of testing, done by the programmers themselves - Beta testing: Later testing, done by future users when the system is almost finalised to collect feedback - White-box testing: Testing the system from the point of view of the programmer, with full knowledge of how it does what it does - Black-box testing: Testing what the system is supposed to do, from the point of view of the user, with no knowledge of how the program does what it does - Unit testing: Testing the modules or components of the system separately - System testing: Testing the system as a whole - Automated testing: Using software to test software - Acceptance testing: The last testing phase once the system is delivered to the user and just before sign-off

evaluate them from their definition, considering testing scope(whether all feature covered) or knowledge (pro or noob)

why test&prototype? - Get Feedback! - code quality, identify and fix bug or vulnerability at early stage, save cost - client trust and satisfaction ### Describe Solution

usability: button, toolbar, menu; complexity, readability, effectiveness accessibility: Text-to-speech; Voice recognition; Braille keyboards; Touch screen; Input from scanner; compatibility: - Language differences/different character set;
- Different conventions of representing various data/currencies, dates, etc.;
- Incompatible software/incompatible hardware;

==legacy system==: outdated application that is no longer maintained, but still has its end users and meets the original need

Update Solution

software update/release strategy: - reason - method: patch, auto update

Migration

requirement of migration: - people: - stakeholder - new training - new skillsets - mindset/emotion - resistance to change - system: - compatibility (legacy system) - benefit(new feature)

in-house / outsource hosting (SaaS, PaaS, IaaS, On-site)

![[_resources/Pasted image 20250918194836.png]]

installation/migration process (implementation for a new computer system) - direct change over - by phase - parallel - pilot run -> example1

evaluate them via dimension of: user, cost, data(compatibility)

Documentation

Technical documentation explains how to install software

documentation’s role: - non-technical user training - trouble shooting/FAQ - sample data/screen - ease transition to new system

different methods of documentation Paper manuals: - Don’t need to be near a computer - Need multiple copies Online manuals: - Can make use of rich media - Can search - Always available Interactive tutorials: - Makes the learning process more interesting Dedicated support teams: - Can give accurate, focused assistance - Increases salary bill

evaluate them from their definition

training methods

Data loss

data loss - cause - human: error, manual deletion, virus/malware - hardware failure, power failure - natural disaster - consequence - cost - reputation - down time - prevention: backup, antivirus, redundancy (duplicate servers, failovers)

when asked for a method to prevent data loss: state the method and its cause (e.g. redundancy to prevent hardware failure)

---